Playback of instant messaging session history

ABSTRACT

Systems, methods and media for playback of instant messaging session history in an instant messaging system by facilitating recording and playback of an instant messaging session history to a user are disclosed. Embodiments may include, during an instant messaging session where one or more instant messaging events occur, determining a timestamp associated with the one or more instant messaging events and recording an indication of the one or more instant messaging events and their associated timestamps. Embodiments may also include receiving one or more playback commands and, in response to the received playback commands, displaying playback of the one or more instant messaging events based on their associated timestamps. The instant messaging events may include one or more of a text message, file transfer, input device movement, or a status indication such as offline, returned from offline, away, returned from away, secure session established, session beginning or session ending.

CROSS-REFERENCES TO RELATED APPLICATIONS

Pursuant to 35 USC §120, this continuation application claims priorityto and benefit of U.S. patent application Ser. No. 11/260,565, entitled“SYSTEMS, METHODS, AND MEDIA FOR PLAYBACK OF INSTANT MESSAGING SESSIONHISTORY”, filed on Oct. 27, 2005, and U.S. patent application Ser. No.12/058,649, entitled “PLAYBACK OF INSTANT MESSAGING SESSION HISTORY”,filed on Mar. 28, 2008, the disclosures of which is incorporated hereinin their entirety for all purposes.

FIELD OF INVENTION

The present invention is in the field of data processing systems and, inparticular, to systems, methods and media for playback of instantmessaging session history in an instant messaging system by facilitatingrecording and playback of an instant messaging session history to auser.

BACKGROUND

Personal computer systems are well known in the art. They have attainedwidespread use for providing computer power to many segments of today'smodern society. Personal computers (PCs) may be defined as a desktop,floor standing, or portable microcomputer that includes a system unithaving a central processing unit (CPU) and associated volatile andnon-volatile memory, including random access memory (RAM) and basicinput/output system read only memory (BIOS ROM), a system monitor, akeyboard, one or more flexible diskette drives, a CD-ROM or DVD-ROMdrive, a fixed disk storage drive (also known as a “hard drive”), apointing device such as a mouse, and an optional network interfaceadapter. One of the distinguishing characteristics of these systems isthe use of a motherboard or system planar to electrically connect thesecomponents together. The use of mobile computing devices, such asnotebook PCs, personal digital assistants (PDAs), sophisticated wirelessphones, etc., has also become widespread. Mobile computing devicestypically exchange some functionality or performance when compared totraditional PCs in exchange for smaller size, portable power, andmobility.

The widespread use of PCs and mobile computing devices in varioussegments of society has resulted in a reliance on computer systems bothat work and at home, such as for telecommuting, news, stock marketinformation and trading, banking, shopping, shipping, communication inthe form of hypertext transfer protocol (http) and e-mail, as well asother services. Many of these functions take advantage of thecommunication abilities offered by the Internet or other networks, suchas local area networks.

A computer system application that continues to increase in popularityis instant messaging (IM). IM systems allow two or more users oncomputer systems such as PCs or mobile computing devices to exchangemessages in real-time (or near real-time). IM systems allow users tomaintain a list of other users, called a buddy or contact list, withwhom they wish to interact. Using the IM system, a user can send aninstant message to any person on their contact list as long as thatperson is on-line. Sending a message to an on-line user opens up aninstant messaging window where each user may type messages that theother user may see, allowing for an electronic “conversation”. Theinstant messaging window typically includes both text input by the useras well as received messages, with new content typically appearing atthe bottom of the window as older content scrolls upwards in the window.Many IM systems also provide chat room capability, where a user can setup a chat room to be shared by multiple users. The chat room operatesunder the same principles as basic instant messaging applied to multipleusers, as each user may type in messages for other users in the chatroom to see. Existing IM systems include Time Warner, Inc.'s AOL®Instant Messenger™ (AIM), Microsoft® Corporation's MSN Messenger™, andYahoo! Inc.'s Yahoo!® Messenger™.

IM systems allow users to exchange text messages as well as files suchas sounds, video, or pictures. The popularity of IM systems is partiallybased on the immediacy of IM systems, particularly when compared toe-mail. This immediacy typically requires both parties in an IM exchangeto be on-line at the same time, in contrast to e-mail. It allows,however, for interactive, back-and-forth exchanges of informationwithout having to perform multiple steps to read, reply, and send areply e-mail. By ensuring that the recipient of a message is availablewhen a message is sent, the message can be delivered and presented tothe recipient nearly instantly (as network conditions allow).

While IM systems continue to increase in popularity, existing IM systemsdo not provide an efficient and effective mechanism for a user to reviewthe real-time performance of an IM session or chat (such as aspects ofspeed or frequency of messaging) after termination of the session. SomeIM systems provide a transcript of an IM session that includes the textof the conversation, but such a transcript lacks the context of thefrequency or speed of messaging. There is, therefore, a need for an easyand effective system to facilitate review of the performance of an IMsession or chat.

SUMMARY OF THE INVENTION

The problems identified above are in large part addressed by systems,methods and media for playing back an instant messaging session.Embodiments may include, during an instant messaging session where oneor more instant messaging events occur, determining a timestampassociated with the one or more instant messaging events and recordingan indication of the one or more instant messaging events and theirassociated timestamps. Embodiments may also include receiving one ormore playback commands and, in response to the received playbackcommands, displaying playback of the one or more instant messagingevents based on their associated timestamps. The instant messagingevents may include one or more of a text message, a file transfer, aninput device movement, a session beginning or a session ending.

Another embodiment provides a machine-accessible medium containinginstructions effective, when executing in a data processing system, tocause the system to perform a series of operations for playing back aninstant messaging session. The series of operations generally includes,during an instant messaging session where one or more instant messagingevents occur, determining a timestamp associated with the one or moreinstant messaging events and recording an indication of the one or moreinstant messaging events and their associated timestamps. The series ofoperations may also include receiving one or more playback commands and,in response to the received playback commands, displaying playback ofthe one or more instant messaging events based on their associatedtimestamps.

A further embodiment provides a client computer system of an instantmessaging system. The client computer system may include acommunications module to send and receive information to and from asecond client computer system and an instant messaging client toinitiate an instant messaging session with the second client computersystem via the communications module and to send and receive one or moreinstant messaging events as part of an instant messaging session. Theclient computer system may also include an instant messaging historymodule to record a history of the instant messaging session, where theinstant messaging history module may also playback the recorded instantmessaging session history.

BRIEF DESCRIPTION OF THE DRAWINGS

Other objects and advantages of the invention will become apparent uponreading the following detailed description and upon reference to theaccompanying drawings in which, like references may indicate similarelements:

FIG. 1 depicts an environment for an instant messaging history systemfor recording and playback of instant messaging history according to oneembodiment;

FIG. 2 depicts a block diagram of one embodiment of a computer systemsuitable for use as a component of the IM history system;

FIG. 3 depicts a conceptual illustration of software components of aclient computer system of the IM history system according to oneembodiment;

FIG. 4 depicts an example of a flow chart for recording an IM sessionhistory and displaying a playback of the IM session history to a useraccording to one embodiment;

FIG. 5 depicts an example of a flow chart for determining trackinginformation relating to input device movement and recording the trackinginformation in an IM history database according to one embodiment;

FIG. 6 depicts an example of a flow chart for receiving highlightingtracking information from another client computer system, displaying anequivalent movement to a user, and recording the equivalent movement inan IM history database according to one embodiment; and

FIG. 7 depicts an example of a flow chart for receiving pointer movementtracking information from another client computer system, displaying anequivalent movement to a user, and storing the equivalent movement in anIM history database according to one embodiment.

DETAILED DESCRIPTION OF EMBODIMENTS

The following is a detailed description of example embodiments of theinvention depicted in the accompanying drawings. The example embodimentsare in such detail as to clearly communicate the invention. However, theamount of detail offered is not intended to limit the anticipatedvariations of embodiments; on the contrary, the intention is to coverall modifications, equivalents, and alternatives falling within thespirit and scope of the present invention as defined by the appendedclaims The descriptions below are designed to make such embodimentsobvious to a person of ordinary skill in the art.

Generally speaking, systems, methods and media for playback of instantmessaging session history in an instant messaging system by facilitatingrecording and playback of an instant messaging session history to a userare disclosed. Embodiments may include, during an instant messagingsession where one or more instant messaging events occur, determining atimestamp associated with the one or more instant messaging events andrecording an indication of the one or more instant messaging events andtheir associated timestamps. Embodiments may also include receiving oneor more playback commands and, in response to the received playbackcommands, displaying playback of the one or more instant messagingevents based on their associated timestamps. The instant messagingevents may include one or more of a text message, a file transfer, aninput device movement, or a status indication such as offline, returnedfrom offline, away, returned from away, secure session established,secure session error, other error, a session beginning or a sessionending.

The system and methodology of the disclosed embodiments allows users torecord and playback histories of instant messaging sessions, including ahistory of any text messages, file transfers, status indications, orinput device movements. By playing back the history of an instantmessaging session, a user may be able to experience the feel or flow ofthe session in a way that a simple transcript cannot accomplish. Thedisclosed system may also be particularly useful when input devicemovements such as highlighting or pointer movements are shared, as thesemovements can be recreated during the playback and provide anotherdimension to the history. As will be described in more detailsubsequently, the disclosed systems and methodologies provide anefficient and effective mechanism for a user to view playbacks of an IMsession.

While specific embodiments will be described below with reference toparticular configurations of hardware and/or software, those of skill inthe art will realize that embodiments of the present invention mayadvantageously be implemented with other substantially equivalenthardware and/or software systems. Aspects of the invention describedherein may be stored or distributed on computer-readable media,including magnetic and optically readable and removable computer disks,as well as distributed electronically over the Internet or over othernetworks, including wireless networks. Data structures and transmissionof data (including wireless transmission) particular to aspects of theinvention are also encompassed within the scope of the invention.

Turning now to the drawings, FIG. 1 depicts an environment for aninstant messaging history system for recording and playback of instantmessaging history according to one embodiment. In the depictedembodiment, the instant messaging (IM) history system 100 includes aplurality of client computer systems 102 in communication with a network104. The IM history system 100 may also include an IM server 106 incommunication with network 104 for managing the instant messagingsystem. In the IM history system 100, the client computer systems 102and the IM server 106 may be located at the same location, such as inthe same building or computer lab, or could be remote. While the term“remote” is used with reference to the distance between the componentsof the IM history system 100, the term is used in the sense ofindicating separation of some sort, rather than in the sense ofindicating a large physical distance between the systems. For example,any of the components of the IM history system 100 may be physicallyadjacent or located as part of the same computer system in some networkarrangements.

Client computer system 102 may include one or more personal computers,workstations, servers, mainframe computers, notebook or laptopcomputers, desktop computers, PDAs, set-top boxes, mobile phones,wireless devices, or the like. In some embodiments, client computersystem 102 may be a computer system as described in relation to FIG. 2.The client computer system 102 may be in wired or wireless communicationwith network 104. Each client computer system 102 may include an IMclient 108, which may be a software application that communicates withthe IM server 106 to facilitate instant messaging by a user of theclient computer system 102 with another user. In this embodiment, the IMclient 108 may transmit information, such as messaging content, statusinformation, or input device movement information, to the IM server 106,which in turn may forward it to a recipient client computer system 102.The IM client 108 may receive information as well, such as messagingcontent, status information, or tracking information, from the IM server106. Alternatively, the IM clients 108 of different client computersystems 102 may communicate with each other directly instead ofcommunicating through the IM server 106.

Each client computer system 102 may also include an IM history module114. The IM history module 114 may record an indication of the historyof an instant messaging session, such as by saving or storing anindication of instant messaging events and an associated timestamp foreach event. An IM session may include any type of instant messagingsession, including multi-party IM chats. Instant messaging events mayinclude any type of event during an instant messaging session, includingthe beginning or termination of the session, status and error messages,text messages or other communications between users, the transfer offiles (e.g., sounds, video, text, etc.) between users, an indication ofinput device movements, audio, video, etc. Status information mayinclude an offline indication, a returned from offline indication, anaway indication, a returned from away indication, a secure sessionestablished indication, a secure session error indication, an othererror indication, a session beginning, a session ending, or any otherstatus information. The IM history module 114 may also facilitateplayback of the instant messaging session to a user, such as byreceiving playback commands from a user and displaying the requestedportion of the IM session to the user. As will be described in moredetail subsequently, the IM history module 114 may advantageously allowa user to view a playback of all or part of an IM session, including thetiming of communications, status changes, input device movements, filetransfers, etc., providing an effective mechanism to view theperformance of an IM session.

Network 104 may be any type of data communications channel, such as theInternet, an intranet, a LAN, a WAN, an Ethernet network, a wirelessnetwork, a proprietary network, or a broadband cable network. Manyinstant messaging systems, such as ICQ, utilize the Internet and areopen to all. Other IM systems, such as AIM™, use proprietary networks,while others such as MSN Messenger™ use semi-private networks. Thoseskilled in the art will recognize, however, that the invention describedherein may be implemented utilizing any type of data communicationschannel.

The IM server 108 may be executing on one or more personal computers,workstations, servers, mainframe computers, notebook or laptopcomputers, desktop computers, or the like. In some embodiment, the IMserver 108 may be a computer system as described in relation to FIG. 2.An example IM server 108 is an International Business MachineCorporation (IBM) eServer® server. In one embodiment, the IM server 106may include an IM system manager 110 to facilitate instant messagingbetween IM clients 108 on different client computer systems 102 bytransmitting and receiving information, such as the identification,status, and/or network address of IM clients 108 and/or client computersystems 102, messaging content, or information relating to movement ofuser input devices. Many different IM system manager 110 applicationsexist, such as ICQ, AIM™, MSN Messenger™, Yahoo!® Messenger™, Jabber,etc.

In an alternative embodiment, the IM server 106 may include an IMhistory module 114 similar to that of the client computer system 102.The IM history module 114 of the IM server 106 may record the history ofmultiple IM sessions for later playback, archiving, or analysis. In thisembodiment, a user of a client computer system 102 may access a playbackof an IM session history by requesting such playback form the IM historymodule 114 of the IM server 106 instead of a local IM history module114. The IM history system 100 may include IM history modules 114 ateither or both of the client computer systems 102 and IM server 106.

In another alternative embodiment, the IM server 106 may also optionallyinclude a tracking information manager 112 when input device movementsare transmitted as part of the IM session. The tracking informationmanager 112 may receive, transmit, and/or analyze tracking informationrelating to input device movement by a user involved in an IM session.For example, the tracking information manager 112 may receive trackinginformation from a sending IM client 108, optionally analyze orotherwise process it, and then transmit the tracking information to arecipient IM client 108. A tracking information manager 112 may not beneeded if, for example, the tracking information is handled in the samefashion as messaging content or if two client computer systems 102 arein direct communication without the IM server 106 being involved. Thetracking information manager 112 may thus allow two users utilizing IMclients 108 on different client computer systems 102 to share inputdevice movements between them. During an IM session, for example, aclient computer system 102 may (such as upon request of the user)receive user input from a user input device representing movement of apointer or other representation of the input device in the instantmessaging window of that user's IM client 108. The user may, forexample, point out text from a few lines back in the history with agesture of their mouse or highlight earlier text with the mouse. Theclient computer system 102 may then convert that input into trackinginformation for transmission and use by a recipient client computersystem 102. The recipient client computer system 102 may then use thetracking information to determine an equivalent movement for the openwindow of its IM client 108 and then to display that equivalent movementto the user in the instant messaging window. If the first userhighlighted text with her mouse, for example, the same text would behighlighted in the instant messaging window for the second user. Inanother example, if the first user used their mouse to circle a word orpoint to a portion of the window, such gesture or motion would berepeated in the second user's window. In this way, a user may simplyhighlight or point her mouse towards particular text in the instantmessaging window and have an equivalent motion be performed for theperson with whom they are communicating.

The systems and methodologies of the disclosed embodiments provide anefficient and effective mechanism for a user to view the performance ofan IM session after the session has completed. By recording a history ofan IM session, a user may playback all or part of the IM session to viewthe occurrence of IM events during real-time. In many cases, viewing theoccurrence of IM events may give a user more insight or information thana simple transcript. A user, for example, could infer hesitation by theother user in noticing a delayed response to a query. The disclosedsystems may also be particularly useful when gestures or other inputdevice movement information is shared as part of an IM session. Thedisclosed system allows a user to view gestures, highlighting, pointermovement or other input device movement during the playback, which maysignificantly enhance the value of the playback experience. A studentviewing a class held as an IM session could, in this example, review theclass at a later time complete with pointer movements made by theprofessor, allowing the user to experience the class as it was initiallyperformed instead of viewing a static transcript. In another example,the disclosed system may provide value when one user responds to a firstquestion from another user shortly after a second question is posed,making it appear on a transcript that the responding user responded tothe second question instead of the first question. Using the disclosedsystem, a playback of the questions and answers will make it clear theresponding user was responding to the first question.

FIG. 2 depicts a block diagram of one embodiment of a computer system200 suitable for use as a component of the IM history system 100, suchas a client computer system 102 or an IM server 106. Other possibilitiesfor the computer system 200 are possible, including a computer havingcapabilities other than those ascribed herein and possibly beyond thosecapabilities, and they may, in other embodiments, be any combination ofprocessing devices such as workstations, servers, mainframe computers,notebook or laptop computers, desktop computers, PDAs, mobile phones,wireless devices, set-top boxes, or the like. At least certain of thecomponents of computer system 200 may be mounted on a multi-layer planaror motherboard (which may itself be mounted on the chassis) to provide ameans for electrically interconnecting the components of the computersystem 200.

In the depicted embodiment, the computer system 200 includes a processor202, storage 204, memory 206, a user interface adapter 208, and adisplay adapter 210 connected to a bus 212. The bus 212 facilitatescommunication between the processor 202 and other components of thecomputer system 200, as well as communication between components.Processor 202 may include one or more system central processing units(CPUs) or processors to execute instructions, such as an IBM® PowerPC™processor, an Intel Pentium® processor, an Advanced Micro Devices Inc.processor or any other suitable processor. The processor 202 may utilizestorage 204, which may be non-volatile storage such as one or more harddrives, tape drives, diskette drives, CD-ROM drive, DVD-ROM drive, orthe like. The processor 202 may also be connected to memory 206 via bus212, such as via a memory controller hub (MCH). System memory 206 mayinclude volatile memory such as random access memory (RAM) or doubledata rate (DDR) synchronous dynamic random access memory (SDRAM).

The user interface adapter 208 may connect the processor 202 with userinterface devices such as a mouse 220 or keyboard 222. The userinterface adapter 208 may also connect with other types of user inputdevices, such as touch pads, touch sensitive screens, electronic pens,microphones, etc. The bus 212 may also connect the processor 202 to adisplay 214, such as an LCD display or CRT monitor, via the displayadapter 210.

FIG. 3 depicts a conceptual illustration of software components of aclient computer system of the IM history system according to oneembodiment. The client computer system 102 of the depicted embodimentincludes an IM client 108, an IM history module 114, a communicationsmodule 302, and a user interface module 304. The client computer system102 may also include an optional input device tracking module 306 andinput device movement translator 308 when input device movement is beingtracked during an IM session. The IM client 108 may initiate IMsessions, receive and transmit user authentication information (i.e.,password and ID), provide for the transmission and receipt of messagingcontent during the IM session, maintain contact lists of other usersassociated with other IM clients 108, encrypt or decrypt communications,or perform other tasks associated with instant messaging. As will bedescribed in more detail subsequently, the IM history module 114 of thedisclosed embodiments may also record and playback to a user a historyof an IM session.

The IM client 108 may utilize the communications module 302 tofacilitate communications to and from an IM server 106 and/or the IMclients 108 of other client computer systems 102 via network 104. Theuser interface module 304 may receive user input from user input devicessuch as a mouse 220 or keyboard 222 and may transmit an indication ofthe received input to other components of the client computer system102, such as the IM history module 114. The user interface module 304may, through display adapter 210, also display the contents of an IMsession either live or as a playback using display 214. Alternatively,the user interface module 304 may use audio, print, or other output inlieu of using a display 214.

The IM history module 114 may include sub-modules such as an IM historyplayer 322 and an IM history database 320 to perform various tasks. TheIM history database 320 may store the history of any IM sessionsperformed by the IM client 108. In one embodiment, IM session historiesare only stored at user request, but in other embodiments IM sessionhistories may be stored by default, based on user configurations, or anyother methodology. The IM history database 320 may also store atimestamp associated with each IM event in an IM history. For example,the IM history module 114 may store a timestamp for each textcommunication, input device movements, file transfers, or other IMevents in the IM history database 320.

The IM history player 322 may playback some or all of an IM session to auser so that they can view the history of the IM session. In embodimentswhere input device movement is part of the recorded playback, the IMhistory player 322 may translate the input device movements as necessaryto accommodate the size or configuration of the playback window. Toaccomplish the playback, the IM history player 322 may access the storedIM history in the IM history database 320 and then playback an IMsession in ‘real-time’ in a playback window. The IM history player 322may playback the session at the same speed at which it was firstperformed, or it may playback the session at a faster or slower ratebased upon user preference, user request, or its own algorithms. The IMhistory player 322 may, for example, playback long periods of inactivityat an accelerated rate as periods of inactivity may provide little valueto the user. Similarly, in another example, the IM history player 322may play periods of high activity during the IM session at a slower rateso that the user may view the details more easily. The IM history player322 may offer any type of command to users, such as selecting IMhistories for review, play, fast forward, rewind, stop, speed of review,bookmarking portions of the IM history, etc. In one example, a user mayrequest the IM history player 322 to begin playing at the 32^(nd) minuteof an IM session. The IM history player 322 may then skip to the 32^(nd)minute of the session and begin playing back the IM session from thatpoint (by accessing the saved session). The subsequent text messages(and any movements or other events) would then be displayed to the userat the same timing and frequency at which they originally occurred. Theuser in this example could also request that the playback be acceleratedor decelerated. One skilled in the art will recognize that user controlof the playback may be accomplished in any fashion.

While the IM history player 322 and IM history database 320 are depictedin FIG. 3 as part of an IM history module 114 as part of a single clientcomputer system 102, other alternatives are possible. In someembodiments, for example, the IM history database 320 may be located ata central database (such as at an IM server 106) that is accessed by anIM history player 322 located at a client computer system 102. Inanother example, the IM history database 320 and the IM history player322 may be located on separate client computer systems 102, such as if auser had a PDA with a IM history player 322 that accessed an IM historydatabase 320 stored on their home personal computer.

In some embodiments, the IM history system 100 may provide for trackinginput device movements during IM sessions, requiring the use of an inputdevice tracking module 306 and/or an input device movement translator308 for the client computer system 102. The input device tracking module306 may determine that the movement of an input device should be trackedand may also track the input device movement signals received by theuser interface module 304. Once input device movement tracking isinitiated, the input device tracking module 306 (through the use of itssub-modules, described subsequently) may determine tracking informationbased on the received input device movement information for transmissionto another client computer system 102 and/or IM client 108.

The input device tracking module 306 may include one or more sub-modulesto track the input device movement and to determine tracking informationbased on the movement. In the disclosed embodiment, the input devicetracking module 306 includes a highlighting tracker sub-module 312 and apointer movement tracker sub-module 314. The highlighting trackersub-module 312 may track highlighting of text by a user in an instantmessaging window. In some embodiments, a user may highlight text byactuating and holding the left-mouse button of their mouse 220 and usingthe mouse 220 to ‘drag’ over the text to be highlighted. When a userhighlights text in their IM window, the highlighting tracking sub-module312 may, in one embodiment, track such a movement by determining thefirst and last characters that are highlighted (with all characters inbetween the first and last characters also being highlighted). Thetracking information in this environment may be the location or identityof the first and last highlighted characters (e.g., from the 5^(th)character to the 37^(th) character), as well as additional informationabout the highlighting such as a special emphasis (e.g., differentcolor, font, size, etc.). Another client computer system 102 accordingto the disclosed system may receive the tracking information and displayan indication of that highlighting in its own IM window, thus allowingthe users to share the highlighting information.

The pointer movement tracker sub-module 314 may track mouse movement bya user in an instant messaging window to determine tracking informationfor use by another client computer system 102 and/or IM client 108. Insome embodiments, a user may move the mouse 220 or other pointing device(e.g., a finger on a touch-screen display, a joystick, a trackball,voice commands, etc.) to cause gestures of a pointer in the instantmessaging window. For example, a user may use the mouse 220 to point toa word with the pointer, point to a block of text, emphasize a portionof their open window, gesture a connection between two chat lines, movethe pointer back and forth over a word or group of words, or otherwisetry to communicate with movement of the pointer. The pointer movementtracker sub-module 314 may receive these input device movements anddetermine tracking information based on them for use by another clientcomputer system 102 and/or IM client 108. In some embodiments, thepointer movement tracker sub-module 314 may determine the trackinginformation by determining the beginning and end characters of amovement (and optionally the speed of that movement).

The input device movement translator 308 may receive trackinginformation from another client computer system 102 and/or IM client 108to translate that into display commands for displaying an equivalentmovement to a user of the recipient client computer system 102. As such,the input device movement translator 308 need only execute on a clientcomputer system 102 on which equivalent movements based on trackinginformation from another client computer system 102 are displayed. Incontrast, the input device tracking module 306 need only be located on aclient computer system 102 that is the source of tracking information,and a particular client computer system 102 may include either or bothof the input device tracking module 306 and the input device movementtranslator 308. The input device movement translator 308 may translateany received tracking information into equivalent movement commands fordisplay to a user. A user with a client computer system 102 equippedwith an input device movement translator 308 may thus view movementssuch as highlighting or pointer movements from another user in theirinstant messaging window.

FIG. 4 depicts an example of a flow chart 400 for recording an IMsession history and displaying a playback of the IM session history to auser according to one embodiment. The method of flow chart 400 may beperformed, in one embodiment, by a client computer system 102 with an IMhistory module 114. Flow chart 400 begins with element 402, where an IMclient 108 may initiate an instant messaging session to start an instantmessaging ‘conversation’. The IM client 108 may, in one embodiment,initiate the session when a user of the IM client 108 either selects acontact with whom they desire to start a session or affirmativelyresponds to a request for a session from another user. At optionalelement 404, the IM history module 114 may receive a request to recordan IM session history for the session initiated at element 402, such asfrom the IM client 108 or from the user via user interface module 304.

Once the IM session has been initiated, the IM history module 114 mayrecord the IM session history throughout the IM session. At decisionblock 406, the IM history module 114 may determine whether an IM eventhas occurred. If an IM event has not occurred, flow chart 400 returns todecision block 406 to await the occurrence of an IM event. If an IMevent has occurred, the IM history module 114 may determine a timestampassociated with the IM event at element 408. In one embodiment, thetimestamp for an IM event should be determined to the level of a secondor less. For an IM session that only includes text conversation, atimestamp accurate to a second or less may provide an acceptable levelof fidelity, while for IM sessions that include animation such as inputdevice movements, timestamp fidelity on the order to tens or hundreds ofmilliseconds may be more useful. Recording less fidelity for thetimestamp accuracy than the times described herein (multiple seconds orlonger) may also be used in exchange for less utility of the disclosedsystem. The fidelity of the timestamp may be a default value, configuredby an administrator or user, or determined in any other fashion.

After determining the appropriate timestamp, the IM history module 114may record an indication of the IM event and the timestamp in the IMhistory database 320 at element 410. In one embodiment, the IM event andthe timestamp may be stored in a table located in the IM historydatabase 320. In an alternative embodiment, the timestamps may be storedin a detailed version of a session transcript. The IM history module 114may next determine if the IM session has terminated (or, alternatively,if the recording of the IM session has been terminated) at decisionblock 412. If the IM session or recording are terminated, the method offlow chart 400 may continue to element 414; otherwise, the method offlow chart 400 may return to decision block 406 for further processingof the next IM event.

Once one or more IM session histories are recorded, the IM historymodule 114 may receive a request to view an IM session history atelement 414. The IM history module 114 may then launch an IM historyplayer 322 to playback an IM session history for the user at element416. At element 418, the IM history player 322 may receive playbackcommands from a user. Playback commands may include any instructionsfrom the user as to the playback of one or more IM session histories,including traditional media content playback commands (e.g., play, fastforward, stop, pause, rewind, increase or decrease speed of playback,etc.), requests to playback one or more IM session histories, requeststo compare IM session histories, history search requests, requests tobookmark or otherwise save a position in a history, etc. After receivingone or more playback commands, the IM history player 322 may at element420 then display a playback of the IM session history in response to theplayback commands The IM history player 322 may determine at decisionblock 422 that playback will be continued and return to element 418 toawait additional playback commands; otherwise, the method of flow chart400 terminates.

In embodiments where input device movement is part of the recordedplayback, the IM history player 322 may translate the input devicemovements as necessary to accommodate the size or configuration of theplayback window (if it is different than the original window size duringthe IM session). The IM history player 322 may use the methodologydescribed in relation to the input device movement translator 308, ormay utilize an input device movement translator 308, to accomplish thistask. A user, for example, who records her session with recordedgestures or other movements (performed by either the user or the personwith whom she is conversing) may view a playback of that IM session in adifferent-sized window than she viewed the original session, possiblynecessitating translation of the recorded input device movements tomovements appropriate for the playback window size.

The methodologies of FIGS. 5-7 may be applicable when input devicemovement is transmitted as part of an IM session. While the disclosedsystems and methodologies are particularly useful when input devicemovement is a possible IM event, tracking of input device movement isnot required for the disclosed systems and methodologies. FIGS. 5-7 andtheir associated description may therefore be considered an optionalembodiment that illustrates the application of the disclosed system andmethodology to a particular type of IM event.

Turning again to the figures, FIG. 5 depicts an example of a flow chart500 for determining tracking information relating to input devicemovement and recording the tracking information in an IM historydatabase according to one embodiment. The method of flow chart 500 maybe performed, in one embodiment, by a client computer system 102 with aninput device tracking module 306 and an IM history module 114. Flowchart 500 begins with element 502, where an IM client 108 may initiatean instant messaging session to start an instant messaging‘conversation’. The IM client 108 may, in one embodiment, initiate thesession when a user of the IM client 108 either selects a contact withwhom they desire to start a session or affirmatively responds to arequest for a session from another user.

At element 504, the input device tracking module 306 may optionallyreceive a request to share input device movement with another user whois party to the instant messaging conversation. The input devicetracking module 306 may receive an indicia of the input device movementfrom the user interface module 304 at element 506. Similarly, the IMclient 108 may also receive any messaging content from the userinterface module 304 at element 508. Messaging content may be text orother content (e.g., image files, sound files, etc.) the user inputs aspart of an instant message.

After receiving a request to share input device movement at element 504and the indicia of input device movement at element 506, the inputdevice tracking module 306 determines how to track the input devicemovement. At decision block 510, the input device tracking module 306may determine whether the received indicia relates to highlighting oftext. If the indicia does relate to text highlighting, the input devicetracking module 306 may track the beginning and ending characterpositions of the highlighted text at element 512. At decision block 514,the input device tracking module 306 may determine whether the receivedindicia relates to pointer movement. If the received indicia does relateto pointer movement, the method of flow chart 500 continues to element516, where the input device tracking module 306 may track characterpositions relating to the mouse movement. In one embodiment, the inputdevice tracking module 306 may track the characters or words in theinstant messaging window that are closest to the beginning and end ofeach mouse movement. In further embodiments, the input device trackingmodule 306 may also track interim characters or words that the pointerpasses over or near during its movement. In this embodiment, the actualpath of the pointer movement may be more precisely tracked. In furtherembodiments, the time the pointer requires to move from one point toanother may also be tracked so that the input device tracking module 306may determine a velocity of the movement.

After the input device tracking module 306 has tracked the input devicemovement, it may next determine the tracking information based on theinput device movement at element 518. Tracking information may be anyinformation used to identify tracked input device movement, such asbeginning or ending characters or words, times or velocity for movement,the type on input, the identity of the input device, the identity of abutton selected, highlighting or ghost pointer emphasis, etc. The inputdevice tracking module 306 may next at element 520 transmit the trackinginformation to the IM client 108 or the communications module 302 fortransmittal. The tracking information may be transmitted separately fromany messaging content, may be cached, or may be transmitted in a packagewith messaging content.

At element 522, the IM history module 114 may determine the timestampassociated with the tracking information and messaging content(similarly to element 408 of flow chart 400). To determine the timestampassociated with the messaging content, the IM history module 114 maysimply use the time at which the messaging content was completed (i.e.,the user pressed an ‘Enter’ or ‘Return’ key). To determine the timestampassociated with tracking information, a more sophisticated methodologymay be required. In one embodiment, the movement may result in twotimestamps, one for the beginning of the movement and one for the end ofthe movement (such as when highlighting text). In other embodiments, amore intricate movement may require more than two timestamps, such aswhen multiple positions in between the start and end points are recorded(such as cursor movement). One skilled in the art will recognize thatany number of timestamps may be utilized for different aspects of aninput device movement. After determining any timestamps, the method offlowchart 500 may continue to element 524, where the IM history module114 may record an indication of the messaging content, trackinginformation, and the associated timestamps in the IM history database320, after which the method either terminates or returns to element 506for further processing.

FIG. 6 depicts an example of a flow chart 600 for receiving highlightingtracking information from another client computer system, displaying anequivalent movement to a user, and recording the equivalent movement inan IM history database according to one embodiment. The method of flowchart 600 may be performed, in one embodiment, by a client computersystem 102 with an input device movement translator 308 and an IMhistory module 114. Flow chart 600 begins with element 602, where an IMclient 108 may initiate an instant messaging session to start an instantmessaging ‘conversation’ with another IM client 108 on a client computersystem 102 with an input device tracking module 306.

The input device movement translator 308 may, at optional element 604,receive a request to display indicia of the other user's input devicemovement. The method of flow chart 600 may then continue to element 606,where the IM client 108 may receive messaging content from the sendingclient computer system 102 whose session was initiated at element 602.Similarly, the input device movement translator 308 may receive trackinginformation (through the communications module 302) from the sendingclient computer system 102 at element 608. As described previously, thetracking information and messaging content may be received as part ofthe same package, separately, or in any other fashion. The IM client 108may display any received messaging content at element 610.

After receiving the tracking information, the input device movementtranslator 308 may next determine at decision block 612 whether thetracking information relates to highlighting of text by analyzing thetracking information. If the tracking information does not relate tohighlighting, the method either terminates, returns to element 604 forcontinued processing, or optionally performs all or part of othermethods (such as that of FIG. 7) for handling other types of inputdevice movement besides highlighting. If the tracking information doesrelate to highlighting, the method of flow chart 600 continues toelement 614, where the input device movement translator 308 may analyzethe tracking information for beginning and ending characters associatedwith the highlighted text or other aspects of the highlighting, such asan indication of increased emphasis (e.g., different color, font, size,boldface, etc.). The input device movement translator 308 may work withthe IM client 108 to display the highlighting (with any requestedemphasis added) from the beginning character to the end character atelement 616. The equivalent movement in the IM window for the recipientuser may be simply the highlighting of the appropriate text in thatwindow. In this fashion, the recipient user may see text highlighted bythe sending user, allowing the users to communicate highlightinginformation via an instant messaging window. In one embodiment, thebeginning and ending characters may be measured from the last characterin the instant messaging window to increase accuracy in situations wherethe windows of different users are displaying different amounts ofhistory (and thus text).

At element 618, the IM history module 114 may determine the timestampassociated with the tracking information and messaging content and atelement 620, the IM history module 114 may record an indication of themessaging content, the tracking information, and any associatedtimestamps in the IM history database 320. Elements 618 and 620 may besubstantially similar to elements 522 and 524, respectively, of FIG. 5and the description will not be repeated in the interest of brevity.After recording the information, the method of flow chart 600 may eitherterminate or return to element 606 for continued processing.

FIG. 7 depicts an example of a flow chart 700 for receiving pointermovement tracking information from another client computer system,displaying an equivalent movement to a user, and storing the equivalentmovement in an IM history database according to one embodiment. Themethod of flow chart 700 may be performed, in one embodiment, by aclient computer system 102 with an input device movement translator 308and an IM history module 114. Flow chart 700 begins with elements 702,704, 706, 708, and 710, which may be substantially similar to elements602, 604, 606, 608, and 610, respectively, of FIG. 6, and the discussionwill not be repeated in the interest of brevity. The received trackinginformation at element 708 may include one or more characters or wordsassociated with the beginning or end of an input device movement, timesor velocity for any input device movement, interim characters or wordsassociated with input device movement, or other information.

After receiving the tracking information, the input device movementtranslator 308 may next determine at decision block 712 whether thetracking information relates to pointer movement of text by analyzingthe received tracking information. If the tracking information does notrelate to pointer movement, the method either terminates, returns toelement 704 for continued processing, or optionally performs all or partof other methods (such as that of FIG. 6) for handling other types ofinput device movement besides mouse movement. If the trackinginformation does relate to pointer movement, the method of flow chart700 continues to element 714, where the input device movement translator308 may analyze the tracking information for characters and/or wordsassociated with the pointer movement. Characters and/or words associatedwith the pointer movement may include beginning, end, or interimcharacters and/or words. The input device movement translator 308 mayalso analyze the tracking information for other aspects of the mousemovement, such as the velocity of movement or a more precise movementpath (with interim points).

After analyzing the tracking information, the input device movementtranslator 308 may at element 716 translate the tracking informationinto one or more incremental movement points associated with therecipient instant messaging window. In one embodiment, the incrementalmovement points may include only the beginning and end points of amovement. In other embodiments, the incremental movement points mayinclude one or more points in between the beginning and ending points.The input device movement translator 308 may then work with the IMclient 108 to display a moving pointer based on the incremental movingpoints at element 718. The pointer may, in some embodiments, be a‘ghost’ pointer that is partially faded so the user does not confuse itwith their own pointer. Other types and configurations of the pointermay be used, including different shapes (e.g., arrows), colors, sizes,intensities, etc. In an alternative embodiment, the pointer may beemphasized similarly to the highlighting of FIG. 6, such as by makingthe ghost pointer flashing, increasing in size, etc.

In this fashion, the recipient user may see equivalent movement viatheir instant messaging window to any mouse or pointer movement by thesending user. The input device movement translator 308 may accomplishthis by utilizing the start and end characters' positions (measuringbackwards from the end of the window) of the recipient window to matchthe same characters in the sending IM window. In one example, if asending user moved their pointer over the 5^(th) word and moved it upthree lines and to the right to the 70^(th) word, the input devicemovement translator 308 can recreate that motion by moving a ghostpointer from the 5^(th) word to the 70^(th) word in its window, even ifthose words are located in different places within the window. The inputdevice movement translator 308, by relying on character or wordlocations instead of geometric position, can thus accommodatedifferences in window sizes, text sizes, amounts of history, etc.,between the sender and recipient window. If the recipient user's instantmessaging window is much narrower than the sending user's window, forexample, an equivalent movement may be steeper on the recipient's window(while still starting and ending on the same characters or words). Inone embodiment, if the sender and recipient user's windows are differentsizes and the equivalent movement would result in scrolling of therecipient window, the input device movement translator 308 may eitherautomatically scroll the IM window or allow the pointer to ‘bump’ theedge of the IM window. An administrator or user may, in someembodiments, configure how the input device movement translator 308handles such a situation.

At element 720, the IM history module 114 may determine the timestampassociated with the tracking information and messaging content and atelement 722, the IM history module 114 may record an indication of themessaging content, the tracking information, and any associatedtimestamps in the IM history database 320. Elements 720 and 722 may besubstantially similar to elements 522 and 524, respectively, of FIG. 5and the description will not be repeated in the interest of brevity.After recording the information, the method of flow chart 700 may eitherterminate or return to element 706 for continued processing.

In general, the routines executed to implement the embodiments of theinvention, may be part of an operating system or a specific application,component, program, module, object, or sequence of instructions. Thecomputer program of the present invention typically is comprised of amultitude of instructions that will be translated by the native computerinto a machine-readable format and hence executable instructions. Also,programs are comprised of variables and data structures that eitherreside locally to the program or are found in memory or on storagedevices. In addition, various programs described hereinafter may beidentified based upon the application for which they are implemented ina specific embodiment of the invention. However, it should beappreciated that any particular program nomenclature that follows isused merely for convenience, and thus the invention should not belimited to use solely in any specific application identified and/orimplied by such nomenclature.

It will be apparent to those skilled in the art having the benefit ofthis disclosure that the present invention contemplates methods,systems, and media for playback of an instant messaging session history.It is understood that the form of the invention shown and described inthe detailed description and the drawings are to be taken merely asexamples. It is intended that the following claims be interpretedbroadly to embrace all the variations of the example embodimentsdisclosed.

What is claimed is:
 1. A method for playing back an instant messagingsession, the method comprising: a processor determining one or moretimestamps, each timestamp being associated with a different instantmessaging event of one or more instant messaging events that haveoccurred during an instant messaging session between a first applicationand a second application, wherein the first and the second applicationspresent different views of the instant messaging session; recording anindication of the one or more instant messaging events and the one ormore timestamps, wherein the one or more instant messaging eventsinclude an input device movement, and wherein the input device movementas made on the first application is translated using a first translationto perform, on the second application, a movement that is equivalent tothe input device movement; and receiving one or more playback commands,and in response, causing a display of playback of at least part of theinstant messaging session in which the one or more instant messagingevents have occurred, wherein the playback of the one or more instantmessaging event is based on the one or more timestamps.
 2. The method ofclaim 1, wherein the display of the playback occurs on a thirdapplication, the third application being configured differently from thesecond application for displaying the at least part of the instantmessaging session, and wherein the display of the playback on the thirdapplication includes a second translation of the input device movementto perform, on the third application, a movement that is equivalent tothe input device movement.
 3. The method of claim 2, wherein the thirdapplication is configured differently from the second application inthat a window size of the third application is different from a windowsize of the second application.
 4. The method of claim 1, wherein theinput device movement comprises highlighting text in the firstapplication, and wherein the input device movement tracks a firstcharacter and a last character of the text being highlighted, andwherein the highlighting comprises tracking special emphasis, thespecial emphasis including one of changing a color of the text beinghighlighted, changing a font of the text being highlighted, and changinga size of the text being highlighted.
 5. The method of claim 1, whereinthe first translation includes tracking a speed of the input devicemovement on the first application to perform the movement on the secondapplication at a speed that is equivalent to the speed of the inputdevice movement.
 6. A computer program product for playing back aninstant messaging session, the computer program product comprising: oneor more computer-readable tangible storage devices; programinstructions, stored on at least one of the one or more storage devices,to determine one or more timestamps, each timestamp being associatedwith a different instant messaging event of one or more instantmessaging events that have occurred during an instant messaging sessionbetween a first application and a second application, wherein the firstand second applications present different views of the instant messagingsession; program instructions, stored on at least one of the one or morestorage devices, to record an indication of the one or more instantmessaging events and the one or more timestamps, wherein the one or moreinstant messaging events include an input device movement, and whereinthe input device movement as made on the first application is translatedusing a first translation to perform, on the second application, amovement that is equivalent to the input device movement; programinstructions, stored on at least one of the one or more storage devices,to receive one or more playback commands, and in response, to cause adisplay of playback of at least part of the instant messaging session inwhich the one or more instant messaging events have occurred, whereinthe playback of the one or more instant messaging event is based on theone or more timestamps.
 7. The computer program product of claim 6,wherein the program instructions to cause the display of the playbackcause the display to occur on a third application, the third applicationbeing configured differently from the second application for displayingthe at least part of the instant messaging session, and wherein thedisplay of the playback on the third application includes a secondtranslation of the input device movement to perform, on the thirdapplication, a movement that is equivalent to the input device movement.8. The computer program product of claim 7, wherein the thirdapplication is configured differently from the second application inthat a window size of the third application is different from a windowsize of the second application.
 9. The computer program product of claim6, wherein the input device movement comprises highlighting text in thefirst application, wherein the input device movement tracks a firstcharacter and a last character of the text being highlighted, andwherein the highlighting comprises tracking special emphasis, thespecial emphasis including one of changing a color of the text beinghighlighted, changing a font of the text being highlighted, and changinga size of the text being highlighted.
 10. The computer program productof claim 6, wherein the first translation further includes tracking aspeed of the input device movement on the first application to performthe movement on the second application at a speed that is equivalent tothe speed of the input device movement.
 11. A computer system forplaying back an instant messaging session, the computer systemcomprising: one or more processors, one or more computer-readablememories and one or more computer-readable tangible storage devices;program instructions, stored on at least one of the one or more storagedevices for execution by at least one of the one or more processors viaat least one of the one or more memories, to determine one or moretimestamps, each timestamp being associated with a different instantmessaging event of one or more instant messaging events that haveoccurred during an instant messaging session between a first applicationand a second application, wherein the first and second applicationspresent different views of the instant messaging session; programinstructions, stored on at least one of the one or more storage devicesfor execution by at least one of the one or more processors via at leastone of the one or more memories, to record an indication of the one ormore instant messaging events and the one or more timestamps, whereinthe one or more instant messaging events include an input devicemovement, and wherein the input device movement as made on the firstapplication is translated using a first translation to perform, on thesecond application, a movement that is equivalent to the input devicemovement; program instructions, stored on at least one of the one ormore storage devices for execution by at least one of the one or moreprocessors via at least one of the one or more memories, to receive oneor more playback commands, and in response, to cause a display ofplayback of at least part of the instant messaging session in which theone or more instant messaging events have occurred, wherein the playbackof the one or more instant messaging event is based on the one or moretimestamps.
 12. The computer system of claim 11, wherein the programinstructions to cause the display of the playback cause the display tooccur on a third application, the third application being configureddifferently from the second application for displaying the at least partof the instant messaging session, and wherein the display of theplayback on the third application includes a second translation of theinput device movement to perform, on the third application, a movementthat is equivalent to the input device movement.
 13. The computer systemof claim 12, wherein the third application is configured differentlyfrom the second application in that a window size of the thirdapplication is different from a window size of the second application.14. The computer system of claim 11, wherein the input device movementcomprises highlighting text in the first application, wherein the inputdevice movement tracks a first character and a last character of thetext being highlighted, and wherein the highlighting comprises trackingspecial emphasis, the special emphasis including one of changing a colorof the text being highlighted, changing a font of the text beinghighlighted, and changing a size of the text being highlighted.
 15. Thecomputer system of claim 11, wherein the first translation furtherincludes tracking a speed of the input device movement on the firstapplication to perform the movement on the second application at a speedthat is equivalent to the speed of the input device movement.
 16. Acomputer program product comprising one or more computer-readabletangible storage devices and computer-readable program instructionsstored on the one or more storage devices, the computer-readable programinstructions, when executed by one or more processors, perform themethod of claim
 1. 17. A computer system comprising one or moreprocessors, one or more computer-readable memories, one or morecomputer-readable, tangible storage devices and program instructionsstored on the one or more storage devices for execution by the one ormore processors via the one or more memories, the program instructions,when executed by the one or more processors, perform the method of claim1.